The LogLevel directive must be enabled.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-26282	WA00620 A22	SV-33207r1_rule	ECAR-1	Medium

Description
The server error logs are invaluable because they can also be used to identify potential problems and enable proactive remediation. Log data can reveal anomalous behavior such as “not found” or “unauthorized” errors that may be an evidence of attack attempts. Failure to enable error logging can significantly reduce the ability of Web Administrators to detect or remediate problems. While the ErrorLog directive configures the error log file name, the LogLevel directive is used to configure the severity level for the error logs. The log level values are the standard syslog levels: emerg, alert, crit, error, warn, notice, info and debug.

Description

The server error logs are invaluable because they can also be used to identify potential problems and enable proactive remediation. Log data can reveal anomalous behavior such as “not found” or “unauthorized” errors that may be an evidence of attack attempts. Failure to enable error logging can significantly reduce the ability of Web Administrators to detect or remediate problems. While the ErrorLog directive configures the error log file name, the LogLevel directive is used to configure the severity level for the error logs. The log level values are the standard syslog levels: emerg, alert, crit, error, warn, notice, info and debug.

STIG	Date
APACHE SITE 2.0 for Unix	2011-12-12

Details

Check Text ( C-33749r1_chk )
Enter the following command: grep "LogLevel" /usr/local/apache2/conf/httpd.conf The command should return the following value: LogLevel warn If the above value is not returned, this is a finding. Note: If LogLevel is set to error, crit, alert, or emerg which are higher thresholds this is not a finding.

Fix Text (F-29385r1_fix)
Edit the httpd.conf file and add the value LogLevel warn.